Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for hex ecosystem metrics collection #11023

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

amazimbe
Copy link
Contributor

What are you trying to accomplish?

Update the hex / elixir ecosystem to add support for gathering ecosystem metrics.

Anything you want to highlight for special attention from reviewers?

This is one in a series of PRs to gather ecosystem meta data and persist it in datadog.

How will you know you've accomplished your goal?

  • I'll be able to see hex / elixir ecosystem metrics in datadog

Checklist

  • I have run the complete test suite to ensure all tests and linters pass.
  • I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
  • I have written clear and descriptive commit messages.
  • I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
  • I have ensured that the code is well-documented and easy to understand.

@github-actions github-actions bot added the L: elixir:hex Elixir packages via hex label Nov 27, 2024
version = SharedHelpers.run_shell_command("mix hex.info")
{
hex_version: version.match(/Hex: \s*(\d+\.\d+(.\d+)*)/)&.captures&.first,
elixir_version: version.match(/Elixir: \s*(\d+\.\d+(.\d+)*)/)&.captures&.first
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems to be a pattern, should this be a constant across ecosystems? Tagging @kbukum1 too

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so. It is ecosystem specific and even within the ecosystem the prefixes are different. One starts with hex, the package manager, and the other starts with elixir the language.

@amazimbe amazimbe force-pushed the amazimbe/hex-ecosystem-metrics branch from f78a788 to 142f767 Compare November 28, 2024 15:52
@amazimbe amazimbe marked this pull request as ready for review November 28, 2024 15:58
@amazimbe amazimbe requested a review from a team as a code owner November 28, 2024 15:58
@amazimbe amazimbe self-assigned this Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L: elixir:hex Elixir packages via hex
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants